Javabean$501015$ - translation to English
Diclib.com
ChatGPT AI Dictionary
Enter a word or phrase in any language 👆
Language:

Translation and analysis of words by ChatGPT artificial intelligence

On this page you can get a detailed analysis of a word or phrase, produced by the best artificial intelligence technology to date:

  • how the word is used
  • frequency of use
  • it is used more often in oral or written speech
  • word translation options
  • usage examples (several phrases with translation)
  • etymology

Javabean$501015$ - translation to English

REUSABLE SOFTWARE COMPONENTS USED IN JAVA PROGRAMMING
Java Bean; Javabean; Java Beans; Javabeans; JavaBean; Java beans; Bean (computing)

Javabean      
n. Javabean, kleine Programmapplikationen in Java geschrieben um einen bestimmten Zweck zu erfüllen (benutzt im Internet - für Aufgaben wie z.B. Zinsberechnung, Wettervorhersagen, u.s.w.)

Definition

JavaBeans
<programming> A component architecture for the Java programming language, developed initially by Sun, but now available from several other vendors. JavaBeans components are called "beans". JavaBeans allows developers to create reusable software components that can then be assembled together using visual application builder tools including Sybase's PowerJ, Borland's JBuilder, IBM's Visual Age for Java, SunSoft's Java Workshop and Symantec's Visual Cafe. JavaBeans support Introspection (a builder tool can analyze how a Bean works), Customisation (developers can customise the appearance and behaviour of a Bean), Events (Beans can communicate), Properties (developers can customise and program with Beans(?)) and Persistence (customised Beans can be stored and reused). http://javasoft.com/beans/. (1997-11-20)

Wikipedia

JavaBeans

In computing based on the Java Platform, JavaBeans is a technology developed by Sun Microsystems and released in 1996, as part of JDK 1.1.

The 'beans' of JavaBeans are classes that encapsulate one or more objects into a single standardized object (the bean). This standardization allows the beans to be handled in a more generic fashion, allowing easier code reuse and introspection. This in turn allows the beans to be treated as software components, and to be manipulated visually by editors and IDEs without needing any initial configuration, or to know any internal implementation details.

As part of the standardization, all beans must be serializable, have a zero-argument constructor, and allow access to properties using getter and setter methods.